Potential fix for https://github.com/RunEdgeAI/coreflow/security/code-scanning/5

To fix the problem, the number and types of arguments passed to vxAddLogEntry must match the format specifiers in its format string. The simplest and safest fix that preserves existing behavior is to add the missing arguments corresponding to the %ux%u placeholders (destination width and height), similar to how the source-dimension log message just above should logically work.

Concretely, in framework/src/vx_graph.cpp at the VX_TYPE_REMAP section, locate the if (remap->dst_width != ... block and its vxAddLogEntry call:

vxAddLogEntry(reinterpret_cast<vx_reference>(this), VX_ERROR_INVALID_DIMENSION,
    "Node: %s: parameter[%u] has an invalid destination dimention %ux%u",
    nodes[n]->kernel->name, p);

This format string has four specifiers: %s, %u, %u, %u. We already pass arguments for the first two (nodes[n]->kernel->name, p), but not for the last two (%ux%u). The correct behavior is to log the actual destination width and height that were found to be invalid, which are remap->dst_width and remap->dst_height. Therefore, we should extend the argument list to:

    nodes[n]->kernel->name, p, remap->dst_width, remap->dst_height);

No new includes or type definitions are needed; remap, dst_width, and dst_height are already in scope and properly typed in this context. This change aligns this log message with the pattern used in the nearby source-dimension log and fixes the formatting-function argument count error without altering control flow or semantics beyond improving the log contents.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.